InfoMagic Internet Tools 1995 April/Internet Tools.iso/dos_win/winsock/maillist/94-04.Z/94-04/text0060.txt

Text File | 1994-04-30 | 16.5 KB | 416 lines

In article <[e-mail]>,
<[e-mail]> writes:
> Path:
reeve.research.aa.wl.com!envoy.wl.com!decwrl!hookup!usc!math.ohio-state.edu!cyb
er2.cyberstore.ca!nntp.cs.ubc.ca!bcsystems!rkobenter
> From: [e-mail]
> Newsgroups: comp.protocols.tcp-ip.ibmpc,alt.winsock
> Subject: Re: Mixing apps and stacks (was: Re: TCP/IP & NFS Software...MS
VxD-based 32-bit TCP/IP...winsock)
> Message-ID: <[e-mail]>
> Date: 29 Mar 94 08:57:07 PST
> References: <[e-mail]> <2n8m1g$[e-mail]>
> Organization: BC Systems Corporation
> Lines: 47
>
> In article <2n8m1g$[e-mail]>, Stephen Heilbronner
<[e-mail]> writes:
> >
> > In article <[e-mail]>, <[e-mail]> writes:
> >> [Stuff deleted]
> >
> >> ....Well, I just tried this experiment.
> >
> >>    - Unloaded the NEWT and Chameleon TCP/IP stuff from my WFWg network.
> >>    - Installed the new MS VxD TCP/IP and got it to work.
> >>    - Ran all my generic winsock apps (Eudora, Trumpet, etc) just fine.
> >>    - Crashed the Netmanage (v4.0) apps (telnet, ftp, ping).
> >>    - Crashed my (NEWT-bundled) PC-X server,
> >>         even after reinstalling to use a generic winsock TCP/IP vice NEWT.
> >
> > On my machine, these Chameleon 4.0 apps run fine on top of Trumpet Winsock
ever
> > since 1.0b1. Im running normal WIndows 3.1.
> >
> >> Pat
> >> --
> >> Pat Hayes, Meteorology, Texas A&M University  *** whoop! ***
> >> [e-mail] <<--email---U$Mail-->> TAMU,CS,TX,77843-3150
> >>          "...yankee by birth...Aggie by the grace of God..."
> >
> > Stephen Heilbronner
> > <[e-mail]>
>
> In an earlier posting I claimed that the Chameleon 4.0 apps where still
> tied via serialization to the NewT stacks' serialization and I speculated
> that this could be the reason why Pat had problems getting the NetManage apps
> to work over the MS-VxD stack.
>
> Yesterday I received a phone call from NetManage explaining that in 4.0
> the serialization has been changed, yes the apps are still  serialized
> but no the stack is (so to speak) unbundled as far as the apps are concerned.
>
> We discussed the problem and can only speculate that maybe some of the
> NetManage DLLs where not available in the configuration.
>
> Anyone else with experiences in this area ...
>
> robert
>
> claims/views/kudos/expressions/suggestions are solely those of the author and
> not shared by the posting organization
>
>
>

Try changing the "Working Directory" property of the ICON so that it doesn't
find the Chameleon WINSOCK first.

Dave Lymburner
Parke-Davis
Ann Arbor, MI 48105
From [e-mail] Mon Apr  4 03:54:49 1994
Received: from bigblue.oit.unc.edu by SunSITE.Unc.EDU (5.65c+IDA/FvK-1.07) with SMTP
          id AA07845; Tue, 5 Apr 1994 09:12:24 -0400
Received: by bigblue.oit.unc.edu (AIX 3.2/UCB 5.64/4.03)
          id AA31441; Tue, 5 Apr 1994 07:52:41 -0500
Received: from GATEWAY by bigblue with netnews
    for [e-mail] ([e-mail])
To: [e-mail]
Date: Mon, 04 Apr 94 10:54:49 PDT
From: Dave Lymburner <[e-mail]>
Message-Id: <2npd6l$[e-mail]>
Organization: Warner-Lambert Parke-Davis Research
Sender: ses
References: <[e-mail]>
Subject: Re: TCP/IP & NFS Software...MS VxD-based 32-bit TCP/IP...winsock


In article <[e-mail]>, <[e-mail]> writes:
> Path:
reeve.research.aa.wl.com!envoy.wl.com!decwrl!hookup!swrinde!cs.utexas.edu!news.
tamu.edu!hayes.tamu.edu!phayes
> From: [e-mail] (Pat Hayes)
> Newsgroups: comp.protocols.tcp-ip.ibmpc,alt.winsock
> Subject: Re: TCP/IP & NFS Software...MS VxD-based 32-bit TCP/IP...winsock
> Date: Sat, 26 Mar 1994 21:03:38 GMT
> Organization: Meteorology, TAMU, USA
> Lines: 61
> Distribution: world
> Message-ID: <[e-mail]>
> References: <[e-mail]>
<[e-mail]> <[e-mail]>
> NNTP-Posting-Host: hayes.tamu.edu
> X-Newsreader: Trumpet for Windows [Version 1.0 Rev A]
>
> >BUT, NetManage has taken the correct approach to the rest of their apps
> >(as has SPRY and FRONTIER and others), they have written to WinSock.
>
> ....Well, I just tried this experiment.
>
>    - Unloaded the NEWT and Chameleon TCP/IP stuff from my WFWg network.
>    - Installed the new MS VxD TCP/IP and got it to work.
>    - Ran all my generic winsock apps (Eudora, Trumpet, etc) just fine.
>    - Crashed the Netmanage (v4.0) apps (telnet, ftp, ping).
>    - Crashed my (NEWT-bundled) PC-X server,
>         even after reinstalling to use a generic winsock TCP/IP vice NEWT.
>
> >So if you want to try a VxD stack then go and get the MS-VxD and layer
WinSock
> >apps such as NetManages' on top.
>
> ....Yes, get MS' TCP/IP, use generic winsock apps, _BUT_ certain vendors'
>    "winsock-compatible" apps may work only with those vendors' stacks. The
>    Netmanage apps I have were looking specifically for NEWT, didn't
>    find it, and crashed.  Same with our NEWT-bundled PC-X.
>
> >My guess is that vendors will bring out their own VxDs because of things
such
> >as NFS and areas not currently covered in WinSock.
>
> ....I read in an earlier article that Netmanage was _NOT_ moving to VxD
>    until Chicago became the defacto standard OS.
>
>    Heh!
>
>    "Hey, Netmanage, the train is leaving..."
>
> >However, they will probably start un-bundling their apps from their stacks
> for those people who want to run over the 'defacto' standard Microsoft TCP/IP
>
> ....I think NCD will sell PC-X as a stand-alone product to work with
>    most TCP/IP stacks; as well as bundled with Netmanage stuff.
>
>
> >On the other hand, I am hearing that we can expect non-MS VxD stacks to be
> >Windows 3.1x compatible,
>
> ....non-WFWg (i.e.- 16-bit) Windows is a dead-end.  Why would vendors develop
>    32-bit stuff for a 16-bit OS?  I don't think so.
>
> >whereas the MS=VxD currently appears only to
> >work in a WfWg scenario. So if you are not a WfWg user then the choice is
clear
> >and at the moment there are only two solutions: Frontier and the PD VxD
stack.
>
^^^^^^^^^^^^^
>
> ....If you're talking about the MS stack, I don't think the MS VxD stack
>    will install on regular (non-WFWG) Windows. At least, not without a _ton_
>    of finagling. If you want to be doing TCP/IP or NFS or other networking;
>    you shouldn't be using a non-WFWg Windows. Get with the program!
>
>
> >Robert
>
> Pat
> --
> Pat Hayes, Meteorology, Texas A&M University  *** whoop! ***
> [e-mail] <<--email---U$Mail-->> TAMU,CS,TX,77843-3150
>          "...yankee by birth...Aggie by the grace of God..."

NetManages IP tools work fine with other vendors WINSOCKs. One must only change
the startup directory in the icon properties so that the tool does not find the
Chameleon WINSOCK first.

Dave Lymburner
Parke-Davis
Ann Arbor, MI 48169
From [e-mail] Sun Apr  3 19:17:00 1994
Received: from bigblue.oit.unc.edu by SunSITE.Unc.EDU (5.65c+IDA/FvK-1.07) with SMTP
          id AA16840; Tue, 5 Apr 1994 10:12:23 -0400
Received: by bigblue.oit.unc.edu (AIX 3.2/UCB 5.64/4.03)
          id AA15433; Tue, 5 Apr 1994 08:52:20 -0500
Received: from GATEWAY by bigblue with netnews
    for [e-mail] ([e-mail])
To: [e-mail]
Date: Sun, 3 Apr 1994 19:17:00 GMT
From: [e-mail] (Paul Steckler)
Message-Id: <[e-mail]>
Organization: College of Computer Science, Northeastern University
Sender: ses
Subject: Where is WinSock spec?

Sorry if this is an FAQ, but I couldn't find it readily.
Where can I get a copy of the WinSock API and spec?

-- Paul
--
  -------------------------------------------------------------------------
 | Paul Steckler          |     URL = http://www.ccs.neu.edu/USER/steck    |
 | [e-mail]      |                                                |
 |-------------------------------------------------------------------------|
From [e-mail] Mon Apr  4 18:38:12 1994
Received: from bigblue.oit.unc.edu by SunSITE.Unc.EDU (5.65c+IDA/FvK-1.07) with SMTP
          id AA21731; Tue, 5 Apr 1994 10:42:24 -0400
Received: by bigblue.oit.unc.edu (AIX 3.2/UCB 5.64/4.03)
          id AA16020; Tue, 5 Apr 1994 09:26:39 -0500
Received: from GATEWAY by bigblue with netnews
    for [e-mail] ([e-mail])
To: [e-mail]
Date: Mon, 4 Apr 1994 18:38:12 GMT
From: [e-mail] (Pat Hayes)
Message-Id: <[e-mail]>
Organization: Meteorology, TAMU, USA
Sender: ses
Subject: PHWIN22 -- ph client for Windows; problem with server setup

Howdy!

Got it, installed it, can't set it up.

Anyone know the verbage to use in the "set default server"
boxes?  Won't take IP address or names.  What goes
in the "Site" box?  The .hlp file doesn't help, either.

Thanks!

Pat

--
Pat Hayes, Meteorology, Texas A&M University  *** whoop! ***
Captain, USAF, AFIT/CIR (15W3A)              [e-mail]
         "...yankee by birth...Aggie by the grace of God..."
From [e-mail] Fri Apr  4 23:32:31 1994
Received: from bigblue.oit.unc.edu by SunSITE.Unc.EDU (5.65c+IDA/FvK-1.07) with SMTP
          id AA21741; Tue, 5 Apr 1994 10:42:25 -0400
Received: by bigblue.oit.unc.edu (AIX 3.2/UCB 5.64/4.03)
          id AA28383; Tue, 5 Apr 1994 09:40:18 -0500
Received: from GATEWAY by bigblue with netnews
    for [e-mail] ([e-mail])
To: [e-mail]
Date: 4 Apr 1994 23:32:31 GMT
From: [e-mail] (Ashok Aiyar)
Message-Id: <2nq82f$[e-mail]>
Organization: Case Western Reserve University, Cleveland, OH (USA)
Sender: ses
References: <2nmasl$[e-mail]>, <[e-mail]>
Reply-To: [e-mail] (Ashok Aiyar)
Subject: Re: NTP (net time protocol) clients?


In a previous article, [e-mail] (David L. Brooks) says:

>In article <2nmasl$[e-mail]> [e-mail] ( ) writes:
>
>>Are there any winsocket compliant NTP (network time protocol) clients out
>>there in the public/share domain?
>
>I know someone who is working on one (he's about two cubicles down from me).
>The NTP part seems to be very solid, and works on a number of stacks.  Once he
>is done, I'm hoping he'll put it on the net.  That's not an easy process
>around here ... you might give it some time.  Feel free to check back with me
>in about, say, a month, if you wish.
>

If this is the client that I have seen (WNTP) then yes, it
is a very nice and solid client.  It will be very nice if it
is released sometime.

Ashok
--
Ashok Aiyar                                      tel: [phone]
Department of Biochemistry                       fax: [phone]
CWRU School of Medicine                  [e-mail]
From [e-mail] Fri Apr  4 15:10:30 1994
Received: from bigblue.oit.unc.edu by SunSITE.Unc.EDU (5.65c+IDA/FvK-1.07) with SMTP
          id AA27026; Tue, 5 Apr 1994 11:12:24 -0400
Received: by bigblue.oit.unc.edu (AIX 3.2/UCB 5.64/4.03)
          id AA22284; Tue, 5 Apr 1994 10:08:20 -0500
Received: from GATEWAY by bigblue with netnews
    for [e-mail] ([e-mail])
To: [e-mail]
Date: 4 Apr 1994 15:10:30 GMT
From: [e-mail] (GEOREF Systems Ltd.)
Message-Id: <2npal6$[e-mail]>
Organization: HookUp Communication Corporation, Waterloo, Ontario, CANADA
Sender: ses
Subject: NT Winsock: Errors From Space

I recently ported some client code from the Unix world to Windows 3.1
using Trumpet Winsock.  After some fiddling, it worked fine.  So now
I take my working Windows app and try to run it on NT.  Wham!  Trouble.

Here's the gist of my Winsock activities:

- Create a datagram type socket with 'socket'.
- Use 'bind' to give it a socket id.
- Use 'sendto' to send a datagram to a server process.
- Use 'recv' to receive a reply from the server.

The 'recv' call returns with WSAENOTCONN.  What?  I created a _datagram_
socket.  My Unix man page for 'recv' does not even list ENOTCONN as a
possible error code for 'recv'.  But the Winsock docs do list it as a
possible error code.  How is this possible, and more importantly,
why is it happening to me on NT and not under Windows 3.1?

Obviously, my Winsock world view is flawed.  Can someone toss some
enlightenment my way?

----------------------------------------------------------------------------
Mike Chapman                                  Email: [e-mail]
GEOREF Systems                                Voice: 519-747-7623
700 Rupert St, Unit B                         Fax:   [phone]
Waterloo, Ontario, N2V 2B5                    UTM:   Zone 17, 537505 4817528
From [e-mail] Tue Apr  5 01:31:20 1994
Received: from relay2.UU.NET by SunSITE.Unc.EDU (5.65c+IDA/FvK-1.07) with SMTP
          id AA01672; Tue, 5 Apr 1994 11:39:41 -0400
Received: from netmanage.com (via netman-gate.netmanage.com) by relay2.UU.NET with SMTP
    (5.61/UUNET-internet-primary) id AAwkig19127; Tue, 5 Apr 94 11:38:45 -0400
Received: from larry.netmanage.com by netmanage.com (4.1/NetManage-1.0)
    id AA01618; Tue, 5 Apr 94 08:30:34 PDT
Date: Tue,  5 Apr 94 08:31:20 PDT
From: Larry Smith <[e-mail]>
Sender: Larry Smith <[e-mail]>
Subject: FW: e-mail address of NetManage?
To: [e-mail]
X-Mailer: Chameleon - TCP/IP for Windows by NetManage, Inc.
Message-Id: <[e-mail]>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII

Dear Mike: send me an order via e-mail to: [e-mail]
Chameleon with educ. discount qty 1 = 360
Internet Chameleon = 200 (dial-up access only)

or if you recently purchase one of the books with our Chameleon Sampler
enclosed let me know.
Regards
****************************************************************
Home of Chameleon TCP/IP for Windows
Larry Smith
Netmange, Inc.
408-973-7171
Remember, the scenery only changes for the lead dog.
****************************************************************
On Tue, 5 Apr 94 10:12:05 PDT  [e-mail] wrote:
>Return-Path: <[e-mail]>
>Received: from zvi-note.netmanage.co.il (zvi.netmanage.co.il) by
netmanage.com (4.1/NetManage-1.0)
>    id AA27271; Tue, 5 Apr 94 00:08:49 PDT
>Date: Tue,  5 Apr 94 10:12:05 PDT
>From: [e-mail]
>Subject: FW: e-mail address of NetManage?
>To: [e-mail]
>X-Mailer: Chameleon 4.00-c, TCP/IP for Windows, NetManage Inc.
>Message-Id: <[e-mail]>
>Mime-Version: 1.0
>Content-Type: TEXT/PLAIN; charset=US-ASCII
>
>
>On Sat, 2 Apr 1994 06:00:43 -0500  Michael Denny wrote:
>>Return-Path: <[e-mail]>
>>Received: from netmanage.com (sunny) by mail. (5.0/SMI-SVR4)
>>    id AA23311; Sat, 2 Apr 1994 03:15:46 +0800
>>Received: from SunSITE.Unc.EDU (calypso-2.oit.unc.edu) by netmanage.com
>(4.1/NetManage-1.0)
>>    id AA13041; Sat, 2 Apr 94 03:07:20 PST
>>Received: from  (localhost.oit.unc.edu) by SunSITE.Unc.EDU
(5.65c+IDA/FvK-1.07)
>with SMTP
>>          id AA24401; Sat, 2 Apr 1994 06:00:43 -0500
>>Errors-To: [e-mail]
>>Date: Sat, 2 Apr 1994 06:00:43 -0500
>>Message-Id: <[e-mail]>
>>Errors-To: [e-mail]
>>Reply-To: [e-mail]
>>Originator: [e-mail]
>>Sender: [e-mail]
>>Precedence: bulk
>>From: [e-mail] (Michael Denny)
>>To: Multiple recipients of list <[e-mail]>
>>Subject: e-mail address of NetManage?
>>X-Listprocessor-Version: 6.0a -- ListProcessor by Anastasios Kotsikonas
>>Content-Type: text
>>Content-Length: 224
>>
>>I want to purchase the  Winsock SDK from NetManage and am looking
>>for their e-mail  address so I can get some more information.  Could
>>someone post/reply with a sales e-mail address for Net Manage?
>>
>>Thanks
>>
>> Michael Denny
>>
>>
>
>************  Home of Chameleon TCP/IP for Windows ****************
>Name: Zvi Alon            Date: 04/05/94             Time: 10:12:05
>                E-mail: [e-mail] (Zvi Alon)
>NetManage, Inc.   10725 DeAnza Blvd. Cupertino, CA 95014, USA
>            Phone: [phone]     FAX: [phone]
>********************** MIME Enclosures OK *************************
>
>

****************************************************************
Home of Chameleon TCP/IP for Windows
Larry Smith
Netmange, Inc.
408-973-7171
Remember, the scenery only changes for the lead dog.
****************************************************************